Mobile communications network, infrastructure equipment, mobile communications device and method

ABSTRACT

A mobile communications network for communicating data to/from mobile communications devices, including a core network part including plural infrastructure equipment, and a radio network part including plural base stations communicating data to/from the mobile communications devices. The mobile communications device communicates an indication of a relative type of data packets for communication via a communications bearer for supporting a communications session of the mobile communications device, the indication used to configure the communications bearer, and provides the communications bearer from the mobile communications device to one or more of the infrastructure equipment via the base stations in accordance with the indication and to control the communication of the data packets via the communications bearer in accordance with the indication communicated via the communications bearer, to control the communication of the data packets from the communications bearer differently to data packets communicated via other communications bearer having a higher priority.

FIELD OF THE INVENTION

The present invention relates to mobile communications networks forcommunicating data to and/or from mobile communications devices,infrastructure equipment and methods for communicating data packets.

BACKGROUND OF THE INVENTION

Mobile communication systems have evolved over the past ten years or sofrom the GSM System (Global System for Mobiles) to the 3G system and nowinclude packet data communications as well as circuit switchedcommunications. The third generation project partnership (3GPP) has nowbegan to develop a mobile communication system referred to as Long TermEvolution (LTE) in which a core network part has been evolved to form amore simplified architecture based on a merging of components of earliermobile communications network architectures and a radio access interfacewhich is based on Orthogonal Frequency Division Multiplexing (OFDM) onthe downlink and Single Carrier Frequency Division Multiple Access(SC-FDMA) on the uplink. The core network components are arranged tocommunicate data packets in accordance with an enhanced packetcommunications system.

At present mobile communications services are dominated by human tohuman (H2H) communications, that is, data which is transmitted by ahuman to another human or at least data that is transmitted forpresentation to a human being. It is now recognised that there is adesire to cater for communications to and/or from machines which arereferred to generally as machine type communications (MTC) or machine tomachine (M2M) communications. MTC communications can be characterised ascommunicating data which has been generated from a source automatically,for example in response to some other stimulus or event reporting someattribute of the machine or some monitored parameter or so-called smartmetering. Thus whilst human communications such as voice can becharacterised as being communications requiring a communications sessionof some minutes with data being generated in bursts of severalmillisecond with pauses there between or video can be characterised asstreaming data at a substantially constant bit rate, MTC communicationscan generally be characterised as sporadically communicating smallquantities of data although it would be appreciated that there is also awide variety of possible MTC communications.

As will be appreciated it is generally desirable to provide a mobilecommunications system and network which can operate efficiently,particularly although not exclusively in respect of the challengespresented by communicating data packets generated by MTC communicationsdevices.

SUMMARY OF THE INVENTION

According to the present invention there is provided a mobilecommunications network for communicating data to and/or from mobilecommunications devices, the mobile communications network comprising acore network part including a plurality of infrastructure equipment, anda radio network part including a plurality of base stations which areprovided with a wireless access interface for communicating data toand/or from the mobile communications devices. The mobile communicationsdevice is arranged in operation to communicate an indication of arelative type of data packets for communication via a communicationsbearer for supporting a communications session of the mobilecommunications device, the indication of the type of the data packetsbeing used to configure the communications bearer. The mobilecommunications network is arranged to provide the communications bearerfrom the mobile communications device to one or more of theinfrastructure equipment via one or more of the base stations inaccordance with the indication of the type of the data packets and tocontrol the communication of the data packets via the communicationsbearer in accordance with the type of data packets being communicatedvia the communications bearer.

By providing an indication of the relative type of the data packets,such as an indication that the data packets are of low priority or aregenerated or being received by a machine type communication application,the mobile communications network can control the communication of thedata packets from the communications bearer differently to data packetscommunicated via other communications bearer having a higher priority.In one example the mobile communications network buffers data packetsfrom a low priority and/or machine type communication application butnot data packets of a higher priority, when the mobile communicationsnetwork is experiencing congestion.

The inventor has recognised that some applications programs such as forexample machine type communications can require the communication ofdata packets cyclically, that is to say at regular intervals. Even ifthese are small amounts of data packets a periodic communication fromapplications can cause congestion on a mobile communications network, ifthe periodic nature of the communication of data packets from theseapplications programs coincides.

According to the present technique a mobile communications device whichis arranged to establish a communications bearer is arranged to providean indication to the mobile radio network when either requesting abearer, establishing a bearer or modifying a bearer which indicatesrelative type of the data to be communicated. In one example, the typeof the indicated data is a low priority indicator and another example isan indicator providing an indication that the data communicated is foran MTC application. Accordingly embodiments of the present techniquecan:

-   -   Dynamically set access indicators per application and/or traffic        type, for example an MTC indication and a low priority        indication so called access/traffic type indications;    -   Set and/or modify indicators in the context information stored        in the system;    -   Gather statistical information of the communications network        entities;    -   Control the mobile communications network in accordance with the        indicated traffic;    -   Modify the system to enable setting up and modifying these        indicators in a flexible manner.

A low priority indicator and an MTC indicator are used in the AS accessmessages as well as in the NAS access messages. The use of theseindicators is governed by configuration parameters which remain usuallyfixed for the time the mobile communications device is attached to thenetwork (some exceptions are possible as explained above). According tothe present technique a scheme is proposed which enables a dynamicconfiguration of communications bearers based on the traffic typegenerated by applications programs. For example an MTC application mayreport some maintenance parameters of a car, an emergency handlingapplication, a mail client synchronizing mailbox every hour, an H2Happlication allowing to make a VoIP call etc.

In one example the control of the communication of the data packetsincludes storing and/or discarding the data packets which are of a lowerpriority and/or and for communication from or to a machine typecommunication application and preferentially not storing and/ordiscarding data packets communicated via other communications bearers ofa higher priority.

As such, for example congestion on the mobile communications network canbe managed by reducing the communication of data packets from lowerpriority or MTC applications.

According to an aspect of the present invention there is provided aninfrastructure equipment for forming part of a mobile communicationsnetwork for communicating data to and/or from a mobile communicationsdevices. The infrastructure equipment is arranged in operation toreceive an indication of a relative type of data packets forcommunication via a communications bearer for supporting acommunications session of a mobile communications device, the indicationof the type of the data packets being used to configure thecommunications bearer, to provide the communications bearer from themobile communications device in accordance with the indication of thetype of the data packets, and to control the communication of the datapackets via the communications bearer in accordance with the type ofdata packets being communicated via the communications bearer.

Further aspects and features of the present invention are defined in theappended claims and include a communications device for forming anassociated group of communications devices and a method of communicatingdata.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments of the present invention will now be described withreference to the accompanying drawings in which like parts have the samedesignated references and in which:

FIG. 1 is a schematic block diagram of a mobile communications networkand mobile communications devices fainting a communication system whichoperates in accordance with the 3GPP Long Term Evolution (LTE) standard;

FIG. 2 is a schematic block diagram of network elements which are shownin FIG. 1 which are arranged to communicate data packets to and/or froma mobile communications devices via a communications bearer for themobile communications network shown in FIG. 1;

FIG. 3 is a schematic representation of a mobile communications deviceillustrating four applications programs operating on the communicationsdevice using two communications bearers;

FIG. 4 is a part schematic diagram part flow diagram illustratingexamples in which the mobile communications device generates andcommunicates bearer establishment or configuration messages;

FIG. 5 is a part schematic diagram part flow diagram illustratingexamples in which the mobile communications device generates andcommunicates messages which include an indication that the data packetsare low priority or that the data packets are generated by an MTCapplication or device;

FIG. 6 is a flow diagram illustrating a process in which a mobilecommunications device establishes or configures a communications bearerfor low priority and/or MTC type data packets reflecting the example ofFIG. 4;

FIG. 7 is a flow diagram illustrating a process in which a mobilecommunications device establishes or configures a communications bearerfor low priority and/or MTC type data packets, which reflects theexample shown in FIG. 6;

FIG. 8 is a schematic block diagram of network elements which are shownin FIG. 1 which are arranged to communicate data packets to and/or froma mobile communications devices showing an up-link communications bearerseparately from a down-link communications bearer;

FIG. 9 is a graphical diagram representing a plot of load on acommunications network in terms of data packets communicated withrespect to time in a twenty four hour period;

FIG. 10 is a schematic block diagram of a serving gateway forming partof the communications chain supporting the communications bearers shownin FIG. 8 adapted in accordance with the present technique;

FIG. 11 is a schematic block diagram of a packet data network gatewayand a serving gateway communicating using a communications bearer with apredetermined quality of service via two routers;

FIG. 12 is a flow diagram illustrating a process in which a mobilecommunications network controls the communication of data packets inaccordance with a relative priority of the data packets from acommunications bearer with respect to the data packets of anothercommunications bearer;

FIG. 13 is a schematic block diagram of the mobile communicationsnetwork and mobile communications devices forming a communication systemshown in FIG. 1 adapted to include a control unit operating inaccordance with the present technique;

FIG. 14 is a flow diagram illustrating a process in which a mobilecommunications network is controlled in accordance with a relativeloading of the network determined in accordance with the presenttechnique; and

FIG. 15 is a schematic block diagram illustrating components of an LTEnetwork which are arranged to distribute an indication that acommunications bearer is for low priority or an MTC type application tonetwork elements.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments of the present invention will now be described withreference to an implementation which uses a mobile communicationsnetwork operating in accordance with the 3GPP Long Term Evolution (LTE)standard. FIG. 1 provides the example architecture of an LTE network. Asshown in FIG. 1 and as with a conventional mobile communicationsnetwork, mobile communications devices (UE) 1 are arranged tocommunicate data to and from base stations 2 which are referred to inLTE as enhanced NodeBs (eNodeB). For transmitting and receiving data viathe wireless access interface the communications devices 1 each includea transmitter/receiver unit 3.

The base stations or eNodeB's 2 are connected to a serving gateway S-GW6 which is arranged to perform routing and management of mobilecommunications services to the communications devices 1 as they roamthroughout the mobile communications network. In order to maintainmobility management and connectivity, a mobility management entity (MME)8 manages the enhanced packet service (EPS) connections with thecommunications devices 1 using subscriber information stored in a homesubscriber server (HSS) 10. Other core network components include thepolicy charging and resource function (PCRF) 12 a packet data gateway(P-GW) 14 which connects to an internet network 16 and finally to anexternal server 20. More information may be gathered for the LTEarchitecture from the book entitled “LTE for UMTS OFDM and SC-FDMA basedradio access”, Holma H. and Toskala A. page 25 ff.

In the following description LTE/SAE terminology and names are used.However embodiments of the present technique can be applied to othermobile communications systems such as UMTS and GERAN with the GPRS corenetwork.

Bearer Configuration

Example embodiments of the present technique provide an arrangement forallowing the coexistence of MTC applications and normal applicationswhich are deployed in common purpose or dedicated devices. At present,the Long Term Evolution/Enhanced Packet Communication (LTE/EPC) system(release-10) proposes to configure a device as either a low prioritydevice or an MTC device. The MTC indication must be used for mobilecommunications devices configured for MTC applications (MTC devices)whereas the low priority indication may be used for all devices i.e.regular human to human as well as MTC devices. The MTC indication isstored as context data at the MME, SGW and PDN-GW whereas a low priorityindication may be stored in the network to assist generation of chargingrecords. A low priority indicator is usually indicated by an AllocationRetention Priority (ARP) value which is one of parameters which definethe quality of service QoS parameters for communications bearers. TheARP values determine how the network should treat data packets sent overthese communications bearers and indirectly how to treat usersgenerating these data packets. These additional bearer parameters suchas an MTC indication is not reflected in QoS parameters and can only betaken into account by logical entities which store this additional MTCindicator information for example in the S-GW and PDN-GW.

At present a device can be configured during the manufacturing processor later with help of the OMA DA and/or (U)SIM OTA procedures. Once thedevice has been configured, the configuration is valid at least for thetime the device is attached to the network. The device cannot change itsconfigured parameters, but the network can change these parameters withthe help of the aforementioned procedures. However this would not happenfrequently as the main purpose of these procedures is to enable initialconfiguration, for example at the first attach or when the equipment hasbeen changed rather than allowing frequent re-configuration. Furthermoreknown mobile communications networks do not establish or configure acommunications bearer in accordance with a low priority or an MTCindication.

According to the present technique a mobile communications device whichis arranged to establish a communications bearer is arranged to providean indication to the mobile communications network when eitherrequesting a bearer or modifying an existing bearer which indicates arelative type of the data to be communicated. In one example, the typeof the indicated data is a low priority indicator and another example isan indicator providing an indication that the data communicated is foran MTC application. Accordingly embodiments of the present techniquecan:

-   -   Dynamically set access indicators per application and/or traffic        type, for example an MTC indication and a low priority        indication so called access/traffic type indications;    -   Set and/or modify indicators in the context information stored        in the system;    -   Gather statistical information of the communications network        entities;    -   Control the mobile communications network in accordance with the        indicated traffic;    -   Modify the system to enable setting up and modifying these        indicators in a flexible manner.

A low priority indicator and an MTC indicator are used in the accessstratum (AS) access messages as well as in the non-access stratum (NAS)access messages. The use of these indicators is governed byconfiguration parameters which remain usually fixed for the time themobile communications device is attached to the network (some exceptionsare possible as explained above). According to the present technique ascheme is proposed which enables a dynamic configuration ofcommunications bearers based on the traffic type generated byapplications programs. For example an MTC application may report somemaintenance parameters of a car, an emergency handling application, amail client synchronizing mailbox every hour, an H2H applicationallowing to make a VoIP call etc.

As explained above, in accordance with the presently proposed LTE/EPCstandard (Release-10) two indicators have been introduced to denote anMTC device and a low priority device. The MTC indication must be usedfor UEs configured for MTC (MTC devices) whereas the low priorityindication may be used for all devices i.e. regular and MTC devices. TheMTC indication is stored as context data at the MME, SGW and PDN-GWwhereas a low priority indication may be stored in the network to assistgeneration of charging records. At present these indications are used togovern access priority at the AS and NAS level. Since these indicationsare associated with the mobile communications device configured in asemi static way, the same indications are always used at the accesstime. This may have an implication that some or all of thecommunications bearers configured by these devices will have the sameindications stored as a part of their context information.

According to the present technique the mobile communications device isallowed to send in the AS and/or NAS messages indicators which maysignal not only a device type (as it is at present) but also applicationtype or traffic type. Typically an application type would be:

-   -   MTC application of a low priority    -   H2H application    -   H2H application of a low priority    -   MTC application

The Application type may reflect traffic types which may have anyproperties from the following list:

-   -   1. Delay tolerant data    -   2. MTC data, automatically generated where the synchronized        access is possible    -   3. Normal priority data    -   4. Low priority data    -   5. High priority data

This information is taken into account when granting initial access. Insubsequent access attempts, the mobile communications device andindirectly an application program triggering the access may usedifferent access indications. The system might also authorize anapplication to use certain access/traffic identifiers. For example, anapplication needs to be digitally signed and at the attach time thesystem grants permission for the application to use certain accessindications. A mobile communications device's operating system checksthe applications' behaviour and verifies that only digitally signedapplications are installed and executed) and/or the system monitorsaccess parameters used by devices whether the device complies with theService Level Agreements (SLA) signed with a service provider or withthe operator.

A further embodiment of the present technique can provide an attachprocedure, which leads to at least the default bearer establishment. Forthe default bearer access indications are stored in the system. However,the mobile communications device can also signal these indicatorsexplicitly.

Should a dedicated bearer be established later, the indicators used atthe access time are stored per bearer. These indicators are suppliedexplicitly by the network if the dedicated bearer establishmentprocedure is initiated by the network or optionally by the mobiledevice. This is applicable to the mobile device's initiated procedure inthe case when access parameters for a bearer are to be different to theaccess parameters used by the mobile device at the access time. Whenmultiple bearers are created in one access attempt the mobilecommunications device or the network can signal them explicitly perbearer in the NAS messages unless the indicators used at the access timeare used for all bearers.

In another example embodiment the network can modify the accessindication information stored in the core network entities by using theexisting bearer modification procedure with a minor enhancement addingnew access parameters to the messages so that it can be signalled whichindications need to be updated/changed.

In another example the mobile communications device may also request thebearer to be modified and can either supply access parameters to be usedor if this information is not provided the indicators used at the accesstime are used instead.

In a further example communications bearers may be provided withdifferent access indications associated with the same or different APNs.The communications bearers can be distinguished in the system becausethe indicators associated with bearers are stored as part of theircontext information. This allows the network to differentiate handlingfor the C-Plane and/or U-Plane data coming from different applicationsand/or data sources. It is possible that the same application maygenerate different traffic types so access indications could vary forsubsequent access attempts. It is possible that the mobilecommunications device may use different access indications to thosestored in the bearer contexts as only the bearer modification procedureis used to modify bearer contexts.

Other examples can provide the following aspects:

-   -   Once the access has been granted other applications may        send/receive data irrespective of their access indicators.        Supposing the access was denied, the application requiring less        restrictions, may still initiate subsequent access attempts        using different indicators. However any application with equal        or lower rights would be blocked.    -   The system may assign priorities to access attempts according to        the list from the highest priority to the lowest such as:        Highest priority: MTC indication set, Normal priority: No        indicators set, Low priority: low priority indication set,        Lowest priority: MTC and low priority indications set;    -   When the system blocks higher priority access all lower priority        access attempts are implicitly blocked with the same restriction        applied to them    -   When the system blocks lower priority access, higher priority        access can be made. If the system also blocks higher priority        access, the restriction implicitly apply to lower priority        accesses unless the system provided restrictions explicitly.    -   There might be more priority levels as indicated by the APR        values.

More detailed example implementations embodying the present techniquewill now be explained. FIG. 2 provides an example illustration in whicha mobile communications device 20 communicates a request for acommunications bearer which may be as part of an attached procedurefollowed by the mobile communications device 20 when attaching to themobile communications network. As shown in FIG. 2, the mobilecommunications device 20 communicates the attach or request message toan eNodeB 2 which is further communicated to a serving gateway S-GW 6which is attached to the eNodeB 2 and then to the packet data gatewayPDN-GW 14. However, in accordance with the present technique the mobilecommunication device 20 may be running one or more applicationsprogrammes.

According to the present technique each of one or more applicationsprograms which are running on the mobile communications device mayaccess one or more communications bearers for supporting communicationsservers provided by those application programs. Thus, as illustrated inFIG. 3 the mobile communications device 20 may include a transceiverunit 30, a control processor 32 and a program execution processor 34.The control processor 32 controls the transceiver unit whichcommunicates radio signals via a wireless access interface to the eNodeB 2 for communicating data packets to and from the mobile communicationsnetwork. As shown in FIG. 3 the processor 34 is arranged to execute aplurality of applications programs in this example four applicationprograms A1, A2, A3 and A4 are being executed by the processor in orderto provide communications service to a user. However, as illustrated inFIG. 3 the four application programs A1, A2, A3, A4 communicate data viatwo bearers 36, 38 which are established by one or more of theapplications programs A1, A2, A3, A4.

As will be familiar to those acquainted with the LTE standard, themobile communications device can establish or modify a default bearer ora dedicated bearer. Examples are shown in FIG. 3. In FIG. 3 when themobile communications device 20 is first switched on the message 22 sentto the mobile communications network is a register/attach message.Accordingly, the mobile communications network establishes a defaultbearer using parameters which may be provided for example in the HSS ofthe mobile communications network. However, the communications device 20may later request a dedicated bearer according to certain parameters bysending a corresponding message to the MME which establishes for examplea dedicated bearer to the same PDN-GW or access points name APN1.Equally the mobile communications device may establish a dedicatedbearer to a different PDN GW with a different access point name APN2.However, the present technique provides an arrangement for signalling arelative priority of the data to be communicated via a default or adedicated bearer 36, 38 which allows the mobile communications networkto differentiate the communication of data packets via those bearers tothe effect of controlling the communication differently depending on thetype of bearer. In one example, if the communications bearer isestablished with an indication that it is a low priority bearer of datapackets or that the data packets are communicated for a MTC typecommunication then one more nodes of the mobile communications networkcan for example buffer those data packets for a pre-determined time whenthe network is congested in order to control that congestion. An exampleof a communication of request messages from the mobile communicationsdevice 20 which provides an indication of either a low priority messageor an MTC configuration message is provided in FIG. 5.

In FIG. 5 a bearer configuration message 22.1 is shown to include a lowpriority message 50 and an MTC configuration indicator 52. However,although the bearer configuration message may be communicated at thepoint of attachment to the mobile communications network in otherexamples the mobile communications device may be communicating accessparameters in order to establish or modify a bearer which may be part ofAS or NAS communications. Accordingly FIG. 5 provides examplesillustrating the communication of the low priority indicator 50 or theMTC indicator 52 for both AS communications and NAS communications.

As will be appreciated with those familiar with LTE, bearers are onlyconfigured once, after which they can be modified or released. However,access parameters can vary per access despite the fact that the beareris established. These access parameters can be at AS level, for examplein the RRC Connection Request and NAS level, for example in the ServiceRequest message.

Returning to FIG. 3 and in accordance with the present technique each ofthe plurality of application programs A1, A2, A3, A4 may communicatedata packets in accordance with a different type having a differentpriority. For example, the first two applications programs A1, A2communicate data packets in accordance with a normal priority whereasthe second applications programs A3, A4 communicate low priority data.In one example if access is granted to a first applications program A1to communicate via one or more of the communications bearers 36, 38access will be granted to the second applications program A2 afterreceiving either a bearer configuration message or an NAS or AS messageproviding a request for the relative priority of the data packets to becommunicated. In another example if one of the second two applicationsprograms A3, A4 communicates a request for low priority communicationsvia the bearers 38 then if this request is denied the MME then datacannot be communicated via the first two applications programs A1, A2unless they request normal priority access and the system grants theaccess. On the contrary, if the applications program A1 is allowed tocommunicate normal priority data then low priority data packets from thethird and the fourth applications programs A3, A4 will be allowed.

As will be appreciated the access to a communications bearer may begranted by different entities within the mobile communications network.For example, at the AS level, the eNodeB manages the access, whereas atNAS level, the MME manages the access. In respect of the bearerconfiguration, this happens once and all nodes on the U-Plane path needto provide authorisation.

Thus, according to the present technique and as illustrated by FIGS. 3,4 and 5, the present technique provides a facility for an applicationsprogram to configure a bearer for communicating data packets with theeffect that the applications program can identify the type of datapackets which are being communicated by the communications bearer andaccordingly the mobile communications network can adapt theconfiguration of the communications bearer so that packets which arecommunicated by that bearer are treated differently with respect to therelative type of those data packets with respect to other types of datapackets. For example the data packets may be identified as either lowpriority or MTC data packets or both and communication adaptedaccordingly. A summary process of illustrating the present technique isprovided in FIG. 6 which is summarised as follows:

S2: The mobile communications device performs an attach or registrationprocedure in which the device initially attaches to the mobilecommunications network. This may be for example when the mobilecommunications device is powered on. As part of the attachment orregistration procedure the mobile communication device communicates somecontext data which includes access parameters. The access parameters inaccordance with the present technique may include an indication of thetype of data packets to be communicated such as a low priority indicatoror an indication that the data packets to be communicated via thecommunications bearer are for an MTC application program running on thecommunications device. The type indicators may include a combination ofthe low priority indicator and the MTC application indicator.

S4: The mobile communications network then creates a communicationsbearer of a default type from the mobile communications device to aPDN-GW using the access parameters provided by the mobile communicationsdevice. The mobile communications network creates a default bearer basedon the access parameters communicated by the mobile communicationsdevice and/or access indications stored in the network such as forexample access indications stored in the mobility management entity(MME) 8 or the homes subscriber server (HSS) 10.

S6: If the access indications stored in the mobile communicationsnetwork indicate that the mobile communications device can be providedwith the communications bearer for the requested type of data packetsindicated by the mobile communications device then the default bearer ofthat type is provided or if the access indications indicate that thecommunications device should not be provided with the communicationsbearer for the requested type then the default communications bearer isset for the access indications stored in the network. Thus the mobilecommunications network controls the type of default bearer which isdeployed to the mobile communications device but considers the type ofbearer requested by the mobile communications device. For example, ifthe access indications stored in the mobile communications network allowa normal type of communications bearer then the request for a lowpriority and or MTC application bearer will be provided as a defaultbearer.

Having established a communications bearer for communicating datapackets from and to the mobile communications device, the mobilecommunications device may have a requirement to be provided with adedicated communications bearer. A dedicated bearer can be establishedusing access parameters or the access parameters for an establisheddedicated bearer can be modified. Similarly the parameters of a defaultbearer can be modified. This may be for example because an applicationprogram executed on the communications device may require thecommunication of data packets of a particular type. Accordingly a flowdiagram illustrated in FIG. 7 may be executed which is summarised asfollows:

S8: An application program on the mobile communications device mayrequest a dedicated bearer as part of the AS or NAS signalling messageswhich may be communicated to the mobile communications network as aresult of conventional signalling activity but may include an indicationof the type of data packets to be communicated. For example, the AS orNAS messages may include an indication that the data packets of a lowpriority or an indication that the data packets communicated are for anMTC application program or combination of these two messages. Thededicated communications bearer may then be established by thecommunications network from an existing PDN-GW or another PDN-GW using adifferent access point name.

S10: Alternatively the mobile communications device may request adedicated bearer for an applications program by communicating a bearermodification message which may include an indication of the type of datapackets to be communicated via the communications bearer as well asother parameters.

S12: The mobile communications network may provide the dedicatedcommunications bearer by establishing a new communications bearer whichoperates in parallel with the default communications bearer.

As will be appreciated in accordance with the present technique anapplication program executing on the mobile communications device isresponsible for signalling the type of data packets which are to becommunicated for a configured communications bearer. In accordance withone example operators of the mobile communications network may set alower tariff for MTC communications and or lower priority communicationsthereby incentivising a user operating the applications program toconfigure the applications program to request a communications bearerfor lower priority data packets and or MTC application data packets.

User Plane Control: Differential Treatment of Data Packets by theNetwork

As explained above, the current state specifying the LTE/EPC system(release 9) is not capable of distinguishing between MTC devices andregular users. However although effort has been spent to address thisdeficiency for C-Plane data, U-Plane data can be only differentiated bycommon set of QoS parameters which are the same for regular and MTCusers. This approach might not be sufficient when the mobilecommunications network handles data generated by these MTCcommunications devices, which may be relevant to situations such as whenthe network is about to be fully utilized and is about to experience oris experiencing congestion. It has been currently proposed that whendata has been received for mobile communications device, which is in theIDLE mode the S-GW is required to buffer the down-link data and sends adownlink Data Notification message to the MME. This may take intoaccount a low priority indication and/or MTC indications. The data hasto traverse up to the S-GW where it is buffered and optionally discardedin some circumstances. This buffering only occurs if the mobilecommunications device is in the IDLE mode when data is to becommunicated to the mobile communications device on the down-link.However the present technique proposes to buffer up-link data to betransmitted from the mobile communications device to the mobilecommunications network.

The mobile communications network also consists of IP routers which canbe placed on the path between the PDN-GW and the S-GW however thesenodes do not understand the notion of bearers and usually use somemarking to apply the same traffic handling for bearers having the sameset of QoS parameters. For example, the communications network might befully utilized or is about to/is experiencing congestion. The routerswould apply standard congestion control mechanisms to start bufferingand later start discarding of data which has a detrimental effect on allusers. Nodes which have some additional information available may act inan intelligent way to support IP routers either in attempt to preventthe congestion from occurring or to assist the routers in the process ofresolving the congestion and preventing the waves or the so calledsynchronization effect when the congestion is resolved the network isstressed with outstanding/backlogged data which leads to yet anothercongestion.

A controller device may be introduced to use an algorithm to control theprocess when the selected group of data is flashed from buffers or isdiscarded. The algorithm might use variable timers controlled byadditional parameters provided by the network such e.g. current systemutilization and/or congestion notifications etc in order to stagger atime at which the buffers are flushed.

FIG. 8 provides an illustrative representation of communication of datapackets from a mobile communications device 20 to a PDN-GW 14 via aneNode B 2 and an S-GW (serving gateway) 6 which illustrates in a onedimensional arrangement the communication of data packets by the mobilecommunications network presented by FIG. 1. As shown in FIG. 8 twocommunications bearers are established for the communications device 20which may be bi-directional but the example shown in FIG. 8 comprise adownlink bearer 80 and an uplink bearer 82.

As explained above, in accordance with a conventional arrangement themobile communications device 20 may be either in an IDLE state or aCONNECTED state. When the communications device 20 is in an IDLE stateand data packets are to be communicated to the mobile communicationsdevice 20 on the downlink then the data packets are stored in a datastore 84 which acts as a buffer within the PDN-GW 14 until the mobilecommunications device has been changed to a CONNECTED state for example.Typically this is done by paging the mobile communications device thatit is to receive downlink data packets.

According to the present technique each of the nodes which have controlof or knowledge of a communications bearer between a mobilecommunications device and a PDN-GW (packet data network gateway) areprovided with an indication of the type of data packets which arecommunicated by that bearer. In the one example the type of data packetsmay be indicated as either low priority data packets or data packets forcommunication to or from an MTC application. By providing knowledge ofthe type of data packets being communicated by the communications bearerthe mobile communications network can control communications of the datapackets for different communications bearers differentially favouringhigh priority data packets from low priority data packets and data fromMTC applications. In one example the control of the communication ofdata packets is performed in order to control congestion on a mobilecommunications network.

FIG. 9 provides an illustrative graphical representation of load on amobile communications network as a result of data packets communicatedon a mobile communications network in a 24 hour period. Thus the x-axisshown in FIG. 9 is a plot of time over a 24 hour period and the y-axisrepresents a load illustrating a number of messages communicated perminute. As can be seen in FIG. 9 the network suffers significant peaksor surges in demand. These peaks in demand may be as a result forexample of applications programs running on for example smart phoneswhich synchronise for example mail boxes or signal requests for anupdate in the status or connectivity and download some data or uploadinformation to a server. As explained this maybe as a result of variouscommunications for example to check mailboxes or pull based methods oraccess social networking portals such as FACEBOOK™ or TWITTER™.

According to the present technique and as indicated above a mobilecommunications device can communicate access parameters for establishinga communications bearer which indicate the type of data packets to becommunicated. Accordingly, one or more of the mobile communicationsdevice 20, the eNode B 72, the serving gateway 76, and or the PDN-GW 74as well as the mobile communications device 20 maybe configured to storedata packets for a low priority bearer and/or an MTC indicated bearer inpreference to data communications packets communicated from otherbearers of a higher priority type to the effect of controlling thecommunication of data packets via the mobile communications network. Asexplained above, in one example, control of the data packets via themobile communications network may be made when the network isexperiencing congestion. Thus, when congestion occurs, data packets fromlow priority sources and or MTC applications are stored in a data bufferuntil such time as congestion is reduced. The data packets in the databuffer may also be discarded in order to reduce congestion.

As indicated above, network elements such as the S-GW buffer down-linkdata for mobile communications devices which are in the IDLE state.However it is not known to provide an arrangement for handling datapackets for the up-link direction or the downlink direction for mobilecommunications devices in the connected mode. According to the presenttechnique a network element such as the S-GW may take into account otherindicators such as the low priority indicator or the MTC applicationindicator, which is stored in its context information. Therefore it isproposed that the S-GW may initially start buffering and later as anoption start discarding data according to the flowing priority list:

-   -   1. low priority data coming from MTC devices    -   2. low priority data    -   3. regular users and/or MTC users    -   4. high priority users (e.g. high priority MTC devices etc.)

This priority lists can be applied separately to buffering and datadiscarding tasks.

When the network notifies an infrastructure component that thecongestion has been reduced or system utilization drops below certainthreshold value the S-GW may start forwarding the buffered data in theorder indicated by the priority list as follows:

-   -   1. Low priority data coming from MTC devices    -   2. low priority data    -   3. regular users and/or MTC users    -   4. High priority users (e.g. high priority MTC devices etc.)

There might be more priority levels as indicated by the ARP value.

This approach allows the communications network to flush data forregular users preventing congestion from re-occurring and avoid the riskof data being discarded by routers.

When the system is close to its full utilization, low priority MTC dataare less likely to cause regular users to suffer and also they arebuffered, for example at the source or in network nodes. As such the MTCdevices will not need to retransmit the data packets and hence the willhave an improved battery and utilization of radio resources (i.e. noneed to retransmit the lost data) will be improved.

An example illustration of one of the nodes shown in FIG. 8 is providedin FIG. 10 which is the serving gateway S-GW 76. As shown in FIG. 10 theS-GW 76 is arranged to control the communication of data packets via theuplink bearer 82. The S-GW 76 includes a control processor 100 whichreceives on an input 102 an indication that the control of data packetsvia the uplink bearer 82 should be buffered for example in order toreduce congestion. In one example the input 102 received by the controlprocessor 100 is an explicit congestion notification (ECN) which isprovided by a lower IP layer which informs the control processor 100that there is congestion on the mobile communications network.Alternatively as explained below the input 102 to the control processor100 may be provided by the MME or from an Operation and MaintenanceCentre which receives other indicators that there is congestion on themobile communications network. In another example explained below theprediction of the congestion is provided by counting the number ofbearers which are provided by the mobile communications network and atype of those bearers and/or the utilisation of these bearers, which arecompared with predetermined thresholds to provide an indication of therelative congestion on the network.

The control processor 100 of the S-GW 76 having determined that thecommunications of the data packets via the communications bearer 82should be controlled then retrieves the data packets from the bearer 82via a connecting channel 104 and stores the data packets by a furtherconnecting channel 106 in a buffer 108. The control processor 100 thenmaintains the data packets in the data buffer 108 until such time as itdetermines that the network is no longer congested in which case it onceagain feeds the data packets out of the buffer into the communicationsbearer 82.

In another example the control processor 100 may discard data packetsfrom the buffer 108 in order for example to control congestion. Forexample the control processor may include a clock 110 which is used todetermine how long the data packets have been stored in the data store108. After a certain time the data packets may be discarded.

The control processor operates to differentially buffer data packets andor discard data packets received by the uplink communications bearer 82independence upon the type of data packets. Thus in one example if thedata packets are low priority data packets then data packets from thecommunications bearer 82 are stored in preference to data packetscommunicated via another bearer 112 thereby differentially communicatingdata packets with respect to the other bearer 112. Accordingly, forexample, congestion can be controlled within the mobile communicationsnetwork.

As will be appreciated the present technique differs from a conventionalarrangement in which an internet protocol (IP) router differentiates thecommunication of IP packets based on a quality of service parameter.Thus the communication from the serving gateway 76 to the PDN-GW 74maybe as illustrated in FIG. 11 via one or more routers 120, 122. Thusthe routers operate at a lower layer to route data packets as IP packetsfrom the PDN-GW gateway 74 to the S-GW 76. However the routers have noknowledge of the type of data packets being communicated via thecommunications bearer and can only use a quality of service (QoS)indication provided in the IP packet header in order to differentiatecommunication of those data packets. The present technique thereforeaddresses the communication at a higher layer of data packets such as IPpackets from the communications network with respect to each bearer ofthe mobile communications network. The mobile communications network canbe arranged to identify for each applications program a type of datapackets communicated, for example as to whether these are low prioritydata packets and or MTC type data packets.

In one example the indication of the congestion received by the S-GW maybe from any of the other communications nodes maybe from a subsequentnode following that node in the chain of communications which faints thecommunications bearer. For example, the serving gateway (S-GW) 76 mayrequest and receive confirmation from the packet data network gateway(PDN-GW) 74 as to whether or not the PDN-GW 74 is congested or not andif not forward the data packets from the buffer 108 and if it iscongested retain the data packets within the buffer 108.

The aforementioned scenarios might become even more relevant when theLTE-Advance is introduced and the core network components are re-usedleading to the situation that data aggregation points such as forexample the S-GW and the back-bone transport network might becomeoverloaded/congested or also the S5/S8 interfaces.

Although the example explained above has been given of an S-GW shown inFIG. 10 it will be understood that any of the eNodeB, the mobilecommunications device 20 or the PDN-GW can include a correspondingcontroller and data buffer, or indeed any other network entity which hasthe additional information available. Accordingly, example embodimentsof the present technique can provide:

-   -   One or more core network entities (e.g. the S-GW) or radio        access network entities which buffer or discard data according        to an intelligent algorithm which takes into account some        additional information stored in the context information and        network input such as e.g. the current system utilization or        congestion notification (e.g. the ECN notification at the IP        layer);    -   A priority list is used to start/stop buffering and/or        discarding for some group of users;    -   An algorithm is used how to link the input data with the        handling functions implemented in some CN entities.

In summary the operation of the mobile communications network to controlthe flow of data packets differentially with respect to a type of thedata packets is provided in FIG. 12 which is summarised as follows:

S20: The mobile communications network establishes a communicationsbearer for communicating data packets from a mobile communicationsdevice to a PDN-GW via a base station (eNodeB) and a serving gateway inaccordance with a conventional operation.

S22: However, one or more of the mobile communications device the basestation, the serving gateway or the PDN-GW maybe provided with anindication of the type of data packets which are to be communicated viathe communications bearer between the mobile communications device andthe PDN-GW established in step S20. The indicated type of data packetsto be communicated in the communications bearer may include anindication that the data packets are of a low priority source and/orthat the data packets are generated from an MTC application.

S24: The communications network may generate an indication that thenetwork is congested and provide a signal to the mobile communicationsdevice, the base station, the serving gateway or the PDN-GW that thenetwork is congested. Alternatively, these elements may receive anindication from an IP layer via an ECN indication that thecommunications network is congested.

S26: The mobile communications device, the base station, the S-GW or thePDN-GW may then control the communication of the data packets via thecommunications bearer to the effect of differentiating the communicationin accordance with the type of communications data packets. For example,if the data packets are from a low priority source or an MTC applicationthen for example the base station, the mobile communications device, theS-GW or the PDN-GW may buffer the data packets but may not buffer datapackets from other communications various with a higher priority. Thusthe data packets of the lower priority are buffered in preference tothose of the higher priority data packets. The data packets with thelower priority may also be discarded after a pre-determined time orafter congestion has reached a pre-determined level.

S28: Optionally one or more of the mobile communications device, thebase station, the serving gateway or the PDN-GW may store the datapackets in a buffer for low priority and/or MTC data packets and thenonly forward the data packets to the next element of the mobilecommunications network if there is a positive indication that there isno congestion present. For example, the eNodeB may store the datapackets for a low priority/MTC communications bearer received from themobile communications device and only forward the data packets to anS-GW if the S-GW provides a positive indication that it is notcongested.

Control of Communications Network Using Context Information Stored inthe Core Network Entities

As explained above, the mobile communications network may store an MTCindicator or a low priority indicator in the core network entities, forexample in the MME, S-GW and/or PDN-GW. These indicators could be usedto count the following:

-   -   The number of bearers established for the MTC use and/or;    -   The number of devices which have some bearers configured for MTC        and/or;    -   The number of devices which have bearers established which are        exclusively used for MTC (the device is purely used for an MTC        application the so called an MTC device or a UE configured for        MTC);    -   Utilisation for bearers of particular types.

In accordance with the further aspect of the present technique themobile communications network of FIG. 1 is shown in FIG. 13 and mayinclude a control unit 130 which is attached to the mobilecommunications network. In one example of the control unit 130 may beattached to the MME 8 or may faun part of the PDN-GW 14 or the S-GW 6.

In operation the control unit 130 counts the number of bearers of eachof the type of communications bearers which are established by themobile communications devices within the network. Thus, if a mobilecommunications device indicates a type of data packets to becommunicated via the communications bearer then this type of datapackets being one of a pre-determined set of types is monitored by thecontrol unit 130 and counted to produce an overall count of the numberof communications bearers communicating each type of data packets.Accordingly, the control unit 130 may generate an indication of thestate of the communications network and determine for example whetherthe communications network is congested and which parts of that networkare congested. Thus, the control unit can then trigger certain actionsof the mobile communications network in accordance with the level ofcongestion.

According to the present technique, at any point in time, the controlunit 130 counts the number of bearers of each of the type ofcommunications bearers which are established by the mobilecommunications devices within the network or measure utilization forbearers of each type. After having performed a count/measurement of agiven status of the network at a certain point in time, the control unit130 may compare these with threshold values. These threshold values canbe statically defined per node or be varied with the system utilizationby devices and bearers. Once the threshold values are determined theactual measured values are compared with threshold values and when atriggering condition is met the following three examples may be used tocontrol the network:

1: The device which performs the measurement: S-GW. The actions are thefollowing:

-   -   The S-GW may inform the MME/PDN-GW that the load generated by        the bearers used for MTC traffic or by MTC devices configured        for MTC is above/below the threshold value;    -   The S-GW may start throttling data for some categories of users;        -   UEs configured for MTC which are of low priority;        -   UE which also run MTC applications which might be of low            priority or not;        -   UE which do not run MTC applications;        -   UE configured for MTC which are not of low priority;        -   Any of the above categories for mobile communication devices            in the IDLE state or in the Connected state    -   The throttling is performed as long as the measured figure is        above the threshold value;    -   The PDN-GW may also start/stop throttling in the same way as the        S-GW based on the indication received from the S-GW (or the        throttling could only be done at the PDN-GW). If the S-GW was        requested to throttle X % of new DL packets for mobile        communication devices in IDLE mode, then this the X figure could        be scalled at the PDN-GW in the following way: X1% (at the        PDN-GW)=X % *(number of all users using this P-GW/number of        users in idle mode and using this P-GW) The indicator may also        include % of data to be throttled for each bearer type;    -   The MME based on the indication received from the S-GW may        trigger the S-GW to be relocated for some groups of devices or        impact the Serving gateway selection process.    -   2: The device which performs the measurement: PDN-GW. The        actions are the following:    -   Likewise the PDN-GW may indicated to the MME that some trigger        conditions are met which will trigger the MME to relocate the        PDN-GW;    -   The MME can also trigger the APN based congestion control        mechanisms, based on an indication received from the PDN-GW;    -   The MME based on indication (bearer type counts and/or        utilization per bearer type) may alter the PDN-GW selection        function to take these data into account.    -   3: The device which performs the measurement: MME. The actions        are the following:    -   The Serving MME for the selected group of devices might be        relocated to another MME available e.g. in the pool of MMEs        serving the MME area;    -   Some groups of devices might be forced to detach from the        system, or detach for a limited time without permission to        attach to another network;    -   Some groups of users when trying to attach or access the system        will be told to either stay in the dormant/de-registered plus        state when they will not be allowed to re-attach to the same        PLMN for X minutes/hours. However they will not try to attach to        other networks during this waiting time, or some groups of        devices will not be allowed to access the system. This can be        signalled in the AS messages at the time of access attempt or        may be signalled for all other devices as well e.g. on the        broadcast channel effectively preventing them to initiate the        access procedure;    -   The MME may also force some groups of users to be handed over to        another cell/eNodeB or even to initiate the inter-RAT or        inter-System handovers.

The operation of the control unit 130 is summarised in FIG. 13 andpresented as follows:

S30: The mobile communications network configures one or morecommunications bearers for communicating data packets from a mobilecommunications device to a PDN-GW via a base station and a S-GW.

S32: The mobile communications network receives an indication from themobile communications device of the type of data packets to becommunicated via the communications bearer and configures thecommunications bearer accordingly. Alternatively, the communicationsnetwork configures the communications bearer in accordance with accessindications stored in the communications network which include anindication of the type of the data packets to be communicated via thecommunications bearer and configures the communications beareraccordingly.

S34: For all of the communications bearers established by thecommunications devices with an indication of the type of the datapackets to be communicated, the mobile communications network counts thenumber of communications bearers of each type this may be performed as afunction of the MME or the PDN-GW for example or measure utilization perbearer type e.g. at the serving gateway or PDN gateway.

S36: The communications network compares the number of each type of thecommunications bearers for each of a plurality of pre-determined typeswith respect to one or more pre-determined thresholds. Thecommunications network can then determine a state of the communicationsnetwork based on the number and/or utilization of communications bearersfor each of the different types. For example, the communications networkdetermine that the network is congested based on a number and/orutilization of each type of the communications bearers and nodecapacity.

S38: The communications network may trigger a congestion indication tothe core network or the radio network parts which include elements whichcontrol the communication of data packets in accordance with the type ofthe data packets. For example, low priority data packets or MTC datapackets may be buffered and other high priority packets are communicatedwithout buffering in preference to the low priority packets. Inaddition, the low priority packets may be discarded in favour ofretaining the high priority packets.

S40: As an alternative the communications network may allowcommunications bearers to communicate data packets from some parts ofthe network and not others. Thus, MTC type communications may be allowedin one part of the network via base stations and a serving gateway butnot communications via another serving gateway. Furthermore, the countof the number of each of the different types of data packetscommunicated by each of the communications bearer can be determined foreach of the nodes of the mobile communications network thereforeproviding a relative distribution of the MTC communications devices inthe mobile communications network.

Distribution of Type of Packet Indicator

FIG. 15 provides a schematic block diagram of a part of the mobilecommunications network shown in FIGS. 1 and 12 which include elementswhich are arranged to establish communications bearers and may includecontext information for those bearers. As shown in FIG. 15 a policycontrol enforcement function PCEF 200 may form part of the PDN-GW 14which is connected to a policy charging and rules function (PCRF) 202.The policy charging and resource function 202 is connected to a homesubscriber server (HSS) 10 and to an application function (AF) 204. Inoperation the application function 204 is arranged to receive anindication of the MTC type and the application type for a communicationsbearer using a Session Initiation Protocol (SIP) message exchange whichis then propagated via the PCRF 202 to the PCEF 200 in the PDN-GW whichcan then be used to communicate a type of the communications bearer toother network elements such as the serving gateway or the eNode B.

Various further aspects and features of the present invention aredefined in the appended claims. Various modifications may be made to theembodiments described above without departing from the scope of thepresent invention. For example, embodiment of the present inventionfinds application with other types of mobile communications networks andis not limited to LTE.

1. A mobile communications network for communicating data to and/or frommobile communications devices, the mobile communications networkcomprising a core network part including a plurality of infrastructureequipment, and a radio network part including a plurality of basestations which are provided with a wireless access interface forcommunicating data to or from the mobile communications devices, whereinthe mobile communications device is arranged in operation to communicatean indication of a relative type of data packets for communication via acommunications bearer for supporting a communications session of themobile communications device, the indication of the type of the datapackets being used to configure the communications bearer, and themobile communications network is arranged to provide the communicationsbearer from the mobile communications device to one or more of theinfrastructure equipment via one or more of the base stations inaccordance with the indication of the type of the data packets and tocontrol the communication of the data packets via the communicationsbearer in accordance with the type of data packets being communicatedvia the communications bearer.
 2. A mobile communications network asclaimed in claim 1, wherein the indication of the type of the datapackets for communication via the communications bearer is generated byan applications program, the communications session being provided bythe applications program using the communications bearer.
 3. A mobilecommunications network as claimed in claim 1, wherein the mobilecommunications device includes an execution processor which is arrangeto operate a plurality of applications programs each of which isarranged to generate the indication of the relative type of the datapackets for communication to and/or from the communications bearer orthe communications bearer and one or more other communications bearersand the mobile communications network is arranged in operation tocommunicate the data packets differently via the communications bearersor the and one or more other communications bearers depending on thetype of the data packets communicated via the or each communicationsbearer.
 4. A mobile communications network as claimed in claim 1,wherein the indication of the type of data bearer is communicated with arequest to establish or to configure or to modify a communicationsbearer.
 5. A mobile communications network as claimed in claim 1,wherein the indication of the type of the data packets is communicatedas an access stratum message, a non-access stratum message or a bearerconfiguration message.
 6. A mobile communications network as claimed inclaim 1, wherein the indication of the type of the data packetscommunicated via the communications bearer, which includes an indicationthat the data packets are for a machine type communication.
 7. A mobilecommunications network as claimed in claim 1, wherein the indication ofthe type of the data packets communicated via the communications bearer,which is associated with the communications bearer, includes anindication of a relative priority of the data packets with respect tothe communication of data packets via other communications bearers ofthe mobile communications network.
 8. A mobile communications network asclaimed in claim 7, wherein the relative priority includes one of moreof an Allocated Retention Priority value and/or a Low Priorityindicator.
 9. A mobile communications network as claimed in claim 1,wherein the control of the communication of the data packets via thecommunications bearer in accordance with a relative priority indicatedby the type of the data packets includes storing the data packets in abuffer for communication of the data packets via the communicationsbearer at a later time in preference to communicating data packets fromother communications bearers at an earlier time with a higher priority.10. A mobile communications network as claimed in claim 9, wherein thecontrol of the communication of the data packets includes discarding thedata packets from the buffer in preference to communicating data packetsfrom other communications bearers.
 11. A mobile communications networkas claimed in claim 1, wherein the control of the communication of thedata packets via the communications bearer in accordance with a relativepriority indicated by the type of the data packets is in response to anindication of congestion of data packets being communicated by themobile communications network.
 12. A mobile communications network asclaimed in claim 1, wherein the type of the data packets communicated isone of more the machine type communications indicator, a low priorityindicator, a regular user indicator or a high priority indicator.
 13. Amobile communications network for communicating data to mobilecommunications devices, the mobile communications network including aplurality of base stations which are provided with a wireless accessinterface for communicating data to or from the mobile communicationsdevices, wherein the mobile communications device is arranged inoperation to communicate an indication of a relative type of datapackets for communicating the data packets via a communications bearerfor supporting a communications session of the mobile communicationsdevice, the indication of the type of the data packets being used toconfigure the communications bearer, and the mobile communicationsnetwork is arranged to provide the communications bearer from the mobilecommunications device to one or more infrastructure equipment via one ormore of the base stations in accordance with the indication of the typeof the data packets and to control the communication of the data packetsvia the communications bearer in accordance with the type of datapackets being communicated via the communications bearer.
 14. A methodof communicating data to mobile communications devices using a mobilecommunications network, the mobile communications network comprising acore network part including a plurality of infrastructure equipment, anda radio network part including a plurality of base stations which areprovided with a wireless access interface for communicating data to orfrom the mobile communications devices, the method comprising receivingan indication of a relative type of data packets for communicating via acommunications bearer for supporting a communications session from themobile communications device, the indication of the type of the datapackets being for use in configuring the communications bearer, andproviding the communications bearer from the mobile communicationsdevice to one or more of the infrastructure equipment via one or more ofthe base stations in accordance with the indication of the type of thedata packets, and controlling the communication of the data packets viathe communications bearer in accordance with the type of data packetsbeing communicated via the communications bearer.
 15. A method asclaimed in claim 14, the receiving the indication of the relative typeof the data packets, includes receiving from an applications program ofthe mobile communications device the indication of the type of the datapackets for communication via the communications bearer, thecommunications session being provided by the applications program usingthe communications bearer.
 16. A method as claimed in claim 14, whereinthe receiving the indication of the relative type of the data packets,includes receiving from each of a plurality of applications programsoperating on the mobile communications device the indication of therelative type of the data packets for communication to and/or from thecommunications bearer or the communications bearer and one or more othercommunications bearers, and the communicating the data packets includescommunicating the data packets differently via the communicationsbearers or the and one or more other communications bearers depending onthe type of the data packets communicated via the or each communicationsbearer.
 17. A method as claimed in claim 14, wherein the communicatingindication of the type of data packets, includes communicating theindication of the type of data packets with a request to establish or toconfigure or to modify a communications bearer.
 18. A method as claimedin claim 14, wherein the communicating indication of the type of datapackets, includes communicating the indication of the type of datapackets as an access stratum message, a non-access stratum message or abearer configuration message.
 19. A method as claimed in claim 14,wherein the indication of the type of the data packets communicated viathe communications bearer, which includes an indication that the datapackets are for a machine type communication.
 20. A method as claimed inclaim 14, wherein the indication of the type of the data packetscommunicated via the communications bearer, which is associated with thecommunications bearer, includes an indication of a relative priority ofthe data packets with respect to the communication of data packets viaother communications bearers of the mobile communications network.
 21. Amethod as claimed in claim 20, wherein the relative priority includesone of more of an Allocated Retention Priority value and/or a LowPriority indicator.
 22. A method as claimed in claim 14, wherein thecontrolling the communication of the data packets via the communicationsbearer in accordance with the type of data packets, includes storing thedata packets in a buffer for communication of the data packets via thecommunications bearer at a later time in preference to communicatingdata packets from other communications bearers at an earlier time with ahigher priority.
 23. A method as claimed in claim 22, wherein thecontrolling the communication of the data packets via the communicationsbearer in accordance with the type of data packets, includes discardingthe data packets from the buffer in preference to communicating datapackets from other communications bearers.
 24. A method as claimed inclaim 14, wherein the controlling the communication of the data packetsvia the communications bearer in accordance with the type of datapackets, includes receiving an indication of congestion of data packetsbeing communicated by the mobile communications network.
 25. A method asclaimed in claim 14, wherein the type of the data packets communicatedis one of more the machine type communications indicator, a low priorityindicator, a regular user indicator or a high priority indicator. 26-27.(canceled)